docs: document implementation matrix #197
Conversation
The idea w/ this matrix is to provide end users a clear picture of what is implemented for each language implementation. Ideally, the matrix will be: 1. auto generated from the kitchen-sink 2. automatically filled in for every implementation via a test In the short term, the automation for fill in the implementation details could be manual, but ideally that would be short-lived for the sake of users and implementors. Signed-off-by: Alex Boten <[email protected]>
Signed-off-by: Alex Boten <[email protected]>
|
Hey @codeboten - I put together a branch with a little demo that shows how the code generation might work: https://github.com/jack-berg/opentelemetry-configuration/tree/generate-compliance-matrix It wrote a fast / dirty script to:
See an example of the output of markdown generation here: https://github.com/jack-berg/opentelemetry-configuration/blob/generate-compliance-matrix/schema.md |
|
@jack-berg Could you check your demo branch ? I can't see the script or the generated markdown. Thanks. |
|
Oops looks like I had some copy paste errors on the links. Fixed. This still needs a decent amount of work before its ready for PR, but I think its conceptually right. |
Thanks, I can see it now. Some suggestion below Instead of presenting:
consider presenting:
Also, extension points are missing. In Samplers for example, I expect an entry for extension points, and the possibility for each SIG to document if extension points are suported or not. |
The idea w/ this matrix is to provide end users a clear picture of what is implemented for each language implementation. Ideally, the matrix will be:
In the short term, the automation for fill in the implementation details could be manual, but ideally that would be short-lived for the sake of users and implementors.